Commit Cargo.lock file
#29
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The `Cargo.lock` file is recommended to be checked in for executables. It allows building and installing the application through cargo in a way that references a common set of dependencies. This is also important for distributions like Fedora, or NixOs, that use the `cargo vendor` command to package the actual version that is released rather than everyone having a package that can essentialy behave differently in non obvious ways. Reference: - https://doc.rust-lang.org/cargo/guide/cargo-toml-vs-cargo-lock.html
|
Looks great, thanks! Should've done this a long time ago |
SoptikHa2
approved these changes
Sep 5, 2024
|
Thank you for being so responsive, this really helps our efforts :). |
13 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
Cargo.lockfile is recommended to be checked in for executables.It allows building and installing the application through cargo in a way
that references a common set of dependencies.
This is also important for distributions like Fedora, or NixOs, that use
the
cargo vendorcommand to package the actual version that isreleased rather than everyone having a package that can essentialy
behave differently in non obvious ways.
Reference: